Garbage Collection - Mark and Sweep

Uneven memory usage

Uneven real-time performance

Stack intensive

Java actually uses a partial mark and sweep algorithm
- The GC thread can get starved
- Accumulation of hard to delete objects
- Object heap fragmentation
- Needs heuristics to get acceptable behavior
  - Increases algorithmic complexity
  - Needs frequent tuning

next